You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This change enhances the NGF technical specifications to include tables of the images provided through our repositories, and adds references to different sections where appropriate linking back to this section.
It also adds a new tab to the Helm installation docs outlining how to install WAF for all Gateways.
This change also adds a section to the WAF configuration guide outlining how the WAF sidecar containers can be optionally customised with different images and other infrastructure settings.
Checklist
Before sharing this pull request, I completed the following checklist:
If my changes involve potentially sensitive information1, I have assessed the possible impact
I have waited to ensure my changes pass tests, and addressed any discovered issues
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩
We still need to update the WAF getting started guide to say that NGF needs to be installed with the nginx image set to nginx-plus-f5waf. Otherwise, isn't the regular NGINX Plus image going to be used if following the installation step in the prerequisites?
We still need to update the WAF getting started guide to say that NGF needs to be installed with the nginx image set to nginx-plus-f5waf. Otherwise, isn't the regular NGINX Plus image going to be used if following the installation step in the prerequisites?
@sjberman Our installation docs don't specify the image to use for plus. If the image is not specified, then the WAF one will be used by default if WAF is enabled but no bespoke image was specified
Our installation docs don't specify the image to use for plus. If the image is not specified, then the WAF one will be used by default if WAF is enabled but no bespoke image was specified
@ciarams87 I see --set nginx.image.repository=private-registry.nginx.com/nginx-gateway-fabric/nginx-plus in the plus installation command in the docs. Which will set it in the NginxProxy resource on installation, so I don't think that default value in the code gets used.
Our installation docs don't specify the image to use for plus. If the image is not specified, then the WAF one will be used by default if WAF is enabled but no bespoke image was specified
@ciarams87 I see --set nginx.image.repository=private-registry.nginx.com/nginx-gateway-fabric/nginx-plus in the plus installation command in the docs. Which will set it in the NginxProxy resource on installation, so I don't think that default value in the code gets used.
@sjberman I forgot to toggle to the plus command in the installation docs so I missed it 🤦🏼♀️ Yeah I'll explain this in the waf docs so
ciarams87
changed the title
NGF: Add supported images to tech specs and guidance around WAF containers
NGF: Add supported images to tech specs and guidance around WAF
May 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
documentationImprovements or additions to documentationproduct/ngfIssues related to NGINX Gateway Fabric
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed changes
This change enhances the NGF technical specifications to include tables of the images provided through our repositories, and adds references to different sections where appropriate linking back to this section.
It also adds a new tab to the Helm installation docs outlining how to install WAF for all Gateways.
This change also adds a section to the WAF configuration guide outlining how the WAF sidecar containers can be optionally customised with different images and other infrastructure settings.
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩